Configure Windows Server 2008 R2 Lab Environment Hands-On Guide

 tagged How To / Hyper-V / Private Cloud / Step-By-Step / Virtualization / Windows Server 2008 R2

clip_image002[4]

Configure Windows Server 2008 R2 Lab Environment Hands-On Guide

Overview:

In this session we will teach you how to setup a cleanly installed Windows Server 2008 R2 SP1 machine to run Hyper-V.  We will create a new virtual machine and make that machine a domain controller.  Then we will make three other virtual machines and get them all communicating.  Upon completing this lab, you will have your cloud foundation built.  The next logical step to build out your cloud is to join your host to the domain.  Then install and configure System Center (download from http://aka.ms/lab.  Installing System Center can take many hours so it is beyond the scope of this session.

The format of the hands on is “keep up with the presenter if you can”. We will be going through the content and you can follow along, if you like. In the lab, we will be setting up the server infrastructure that will be needed to deploy System Center 2012 basic components in your own lab. This will include AD infrastructure and virtual machines that you can use to later install System Center (VMM, Operations Manager, Orchestrator, Service Manager) including instructions on getting networking between the machines working. If you do want to try to keep up, in the hands-on lab, make sure you bring a laptop with plenty available disk space.

 

CAMP HANDS-ON LAB REQUIREMENTS: If you want to participate in Hands-On please bring your laptop with the following minimum requirements:

Assumptions:

a)       Your hardware meets the requirements to run Windows Server 2008 R2 SP1 with Hyper-V

b)       You already have Windows Server 2008 R2 SP1 Running on your computer

c)        Network drivers are installed and working  LAN and Wireless

d)       Wireless Feature Enabled

e)       Hyper-V Role Installed

Please COPY:  DO NOT MOVE the contents from the USB to your Desktop. Please return the USB keys

Steps overview:

1)      Prepare for lab build

a.       Create folder to store New Virtual Machines (eg. C:VM)  This should be on a physical disk preferably internal but external will work (will be slower)

b.      Copy from USB Drives (DO NOT MOVE) 2008r2sp1-Sysprep-VM.zip (from the root or OS folder of USB stick)

                                                               i.      Please COPY:  DO NOT MOVE the contents from the USB to your Desktop. Please return the USB keys right away

                                                             ii.      Extract the contents of the zip file  to your VM (C:VM ) folder (right-click, Extract All, Extract)

c.       Register for and start download of System Center 2012 using link provided by lab instructor(s)

2)      Configure Virtual Networks – HOL Create a New Internal Virtual Network “Demo Lab”

a.       In Hyper-V Manager, in the Actions pane, click Virtual Network Manager.

b.      In the Virtual Network Manger window, click Internal, and then click Add. Internal networks are used to communicate between the host computer and virtual machines on the host computer.

c.       In the Name field, type “Demo Lab”, and then click OK.

d.      Click Start, right-click Network, and then click Properties.

e.       On the Network and Sharing Center window, click Change adapter settings.

f.        Note our new network is available

                                                               i.      Right-click the Local Area Connection that is connected to the Demo Lab, and then select Rename type Demo Lab press Enter. 

g.       In order for the host computer to communicate with the virtual machines using this network, you need to configure the network adapter with an IP address configuration that is able to communicate with the virtual machines.  (eg. 192.168.160.5).  Right-click the Demo Lab connection, then click Properties.  Click Internet Protocol Version 4 (TCP/IPv4), then click Properties.  Click Use the following IP Address:  

                                                               i.      Enter IP Address:  192.168.160.5

                                                             ii.      Enter Subnet mask: 255.255.255.0

                                                           iii.      Default Gateway:  MUST LEAVE BLANK!!!!

                                                           iv.      Preferred DNS Server: 192.168.160.10  

                                                             v.      Click OK to Close the IP dialog box

                                                           vi.      Close the Demo Lab Properties dialog box, and then close the Network Connections window.

3)      Deploy a New VM – Create new virtual machine to be used as a Domain Controller

a)      From the Hyper-V Host, open Hyper-V Manager.

b)      In the Actions pane, click New, click Virtual Machine.

c)       The New Virtual Machine Wizard appears. Click Next (before you begin screen).

d)      On the Specify Name and Location page,

a.       Name field, type a name  Lab-DC

b.      Select Store the virtual machine in a different location check box. In the Location field, type C:VM, (or the location you will be storing your VMs) click Next.

e)      On the Assign Memory page, click Next.  This value can be changed later.

f)        On the Configure Networking page, in the Connection list, click Demo Lab, click Next.

g)       On the Connect Virtual Hard Disk page  Click Attach a virtual hard disk later

h)      Click Finish

i)        Right-click Lab-DC select settings

a.       Click Memory in left pane of the Lab-DC Settings, change to Dynamic

b.      Click IDE Controller 0 in left pane of the Lab-DC Settings, Click Add to add a hard drive

c.       Click New click Next select Differencing on the choose disk type dialog, click Next

d.      Specify Name and Location Wizard page

                                                                                       i.      Type Name:DC-Boot.vhd

                                                                                     ii.      Browse to Location: C:VMLab-DC; click Select Folder; click Next

e.       Configure Disk Wizard Page (You can download sysprep image from Dan’s Blog)

                                                                                       i.      Browse to C:VM select 2008r2sp1-Sysprep-VM.vhd Click Open, then Finish; then OK

j)        Boot Virtual Machine – In Hyper-V Manager; Right-Click Lab-DC select Start; then Lab-DC double-click to Open

a.       Enter Administrator password and other configuration settings as desired

a.       [Recommended but Optional] Set to ALWAYS auto-start – Right Click on virtual machine – Select Properties – at the bottom of the left pane select Automatic Start Action – then on the right pane select always start this virtual machine automatically. Click OK

b.      Boot Virtual Machine

                                                               i.      Enter Administrator password and other configuration settings as desired

                                                             ii.      Attach  VM to “Demo Lab” network – if you skipped that step when you created the machine

c.       Change Computer Name to Lab-DC: Start – Right-Click  My Computer – Change Settings – Change – Type Lab-DC in computer name, OK, Ok, Reboot now

4)      Login to New Virtual machine DC-Lab – Install the Integration Services

a.       From the Hyper-V host, select the VM which was just deployed and click Start in the right actions pane

b.      Click Connect.

c.       On the Action menu in the Virtual Machine Connection window, click Insert Integration Services Setup Disk.

                                                               i.      If this option is unavailable or nothing happens it means that the Integration Services have already been installed or the virtual machine is not finished starting.

d.      In the Upgrade Hyper-V Integration Services dialog box, click OK.  Click Yes when prompted to restart

e.       In the AutoPlay window, click Install Hyper-V Integration Services. If you do not have AutoPlay turned on you can run the installation from the CD under My Computer.

5)      Configure VM Domain Network

a.       Login to VM

b.      Click Start, right-click Network, and then click Properties.

c.       On the Network and Sharing Center window, click Change adapter settings.

d.      Right-click the Local Area Connection that is connected to Demo Lab, and then select Rename type Demo Lab Domain then Enter. 

e.       Right-click the Demo Lab Domain connection, then click Properties.  Click Internet Protocol Version 4 (TCP/IPv4), then click Properties.  Click Use the following IP Address:  

                                                               i.      Enter IP Address:  192.168.160.10

                                                             ii.      Enter Subnet mask: 255.255.255.0

                                                           iii.      Default Gateway:  MUST LEAVE BLANK!!!!

                                                           iv.      Preferred DNS Server: 127.0.0.1  

                                                             v.      Click OK to Close the IP dialog box

                                                           vi.      Close the Demo Lab Domain Properties dialog box, and then close the Network Connections window.

6)      Create the DemoLab Domain – In your Lab-DC Virtual Machine, go to Start, type in dcpromo  accept the elevation request 

a.       Create New Domain in New forest

b.      FQDN of forest: demolab.loc or a domain name of your choice. (eg. itproguru.loc, or YourName.loc)

c.       Forest Functional Level – change to Windows Server 2008 R2; Next

d.      Next again on the Additional Domain Controller Options (DNS should be checked)

e.       Confirm Yes on the delegation for DNS warning message

f.        Location of files:  Keep the defaults; Next

g.       Password: P@ssword (or whatever you like); Next

h.      Summary Screen;  Next; Turn on Checkbox to Reboot on completion

i.         Set Password Policy: Start-Administrative Tools- Group Policy Management

                                                               i.      Expand ForestDomainsYourDomainName; right-click Default Domain Policy select Edit

                                                             ii.      Expand Computer ConfigurationPoliciesWindows SettingsSecurity SettingsAccount PoliciesPassword Policy

1.       Enforce password history = 0;

2.       Maximum age = 0; minimum password age = 0;

3.       Password must meet complexity: disabled?

7)      Create and configure new machines for SCOM, SCOR, SCVMM

a.       Repeat Step 3 above for each of the following machine names

                                                               i.      Lab-VMM  replace Lab-DC with Lab-VMM

                                                             ii.      Lab-OM  replace Lab-DC with Lab-OM

                                                           iii.      Lab-OR  replace Lab-DC with Lab-OR

b.      Repeat Step 4 on Lab-VMM, Lab-OM and Lab-OR 

c.       Configure VM Domain Network on all three new machines

                                                               i.      Login to VM – Click Start, right-click Network, and then click Properties.

                                                             ii.      On the Network and Sharing Center window, click Change adapter settings.

                                                           iii.      Right-click the Local Area Connection that is connected to Demo Lab, and then select Rename type Demo Lab Domain then Enter. 

                                                           iv.      Right-click the Demo Lab Domain connection, then click Properties.  Click Internet Protocol Version 4 (TCP/IPv4), then click Properties.  Click Use the following IP information:  

Machine

IP Configuration

Lab-VMM

IP Address:  192.168.160.11

Enter Subnet mask: 255.255.255.0

Default Gateway: LEAVE BLANK!!!!

Preferred DNS Server: 192.168.160.10 

Lab-OM

IP Address:  192.168.160.12

Enter Subnet mask: 255.255.255.0

Default Gateway: LEAVE BLANK!!!!

Preferred DNS Server: 192.168.160.10 

Lab-OR

IP Address:  192.168.160.13

Enter Subnet mask: 255.255.255.0

Default Gateway: LEAVE BLANK!!!!

Preferred DNS Server: 192.168.160.10 

 

                                                             v.      Click OK to Close the IP dialog box

                                                           vi.      Close the Demo Lab Domain Properties dialog box, and then close the Network Connections window.

1.       Install Integration Components: Click Connect.  On the Action menu in the Virtual Machine Connection window, click Insert Integration Services Setup Disk.

2.       Click OK (to upgrade).  Click Yes when prompted to restart

8)      Configure Firewall on host and all guest to allow ping:

a.    Start –  Control Panel – System and Security – Windows Firewall – Advanced Settings – Inbound Rules

b.      File and Printer Sharing (Echo Request – ICMPv4-in) – Right Click and Select Enable Rule

c.       http://aka.ms/ping7  for detailed instructions – confirm you can ping to and from all!

 

 End Session: Hands-On!

 


 

 Next steps when you get back to home or office

9)      Configure Wireless Virtual Network on Host – HOL Create a New Internal Virtual Network “VM Wireless”

a.       In Hyper-V Manager, in the Actions pane, click Virtual Network Manager.

b.      In the Virtual Network Manger window, click Internal, and then click Add. Internal networks are used to communicate between the host computer and virtual machines on the host computer.

c.       In the Name field, type “VM Wireless”, and then click OK.

d.      Click Start, right-click Network, and then click Properties.

e.       On the Network and Sharing Center window, click Change adapter settings.

f.        Note our new network is available

                                                               i.      Right-click the Local Area Connection that is connected to the VM Wireless, and then select Rename type VM Wireless press Enter

                                                             ii.      Right-click the VM Wireless Connection, and then click Properties.

g.       Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.

h.      Click Advanced button; click DNS tab; turn OFF checkbox Register this connection’s addresses in DNS; OK

i.         Bridge Connections:  Click “VM Wireless” network to select it, hold the control key while you also select your physical wireless network connection to multi-select; Right-Click on selected connection; select Add to Bridge

j.         Close the Network Connections window. Close the Local Area Connection dialog box.      

10)   Configure Wireless on VM’s

a.       Right-click VM-Name select settings

b.      Click Add Hardware (Top) left pane of the Settings, select Network click Add

c.       Do NOT Connect to a network adapter yet … Just click OK

d.      Start the VM and login

e.       Click Start, right-click Network, and then click Properties.

f.        On the Network and Sharing Center window, click Change adapter settings.

g.       Note our new network is available

                                                               i.      Right-click the new Local Area Connection that is not connected  then select Rename type VM Wireless press Enter

                                                             ii.      Right-click the VM Wireless Connection, and then click Properties.

h.      Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.

i.         Click Advanced button; click DNS tab; turn OFF checkbox Register this connection’s addresses in DNS; OK

j.         Click File Settings (Gust Menu) click the second network adapter (not currently connected) change the network to VM Wireless

k.       Your Guests will now have Internet connectivity as long as the host has wireless internet connectivity.

11)   Join the Host to your New DC – note, if you are already on a domain please consider the consequences.

12)   Start Installing System Center 2012 on your new servers J 

a.       Lab-OR Unified Installer,  Orchestrator, Service Manager, SQL Server

b.      Lab-VMM System Center Virtual machine Manager

c.       Lab-OM Operations Manager


 

Appendix

Stubborn NIC

  • Install the Intel Ethernet driver from manufacturer (eg 6irf24ww_764). You are running the installer but it does not really install it. However, it does put the driver on disk so you can manually select it later.
  • Start | type Device Manager | Press ENTER
  • Right-click “Ethernet Controller” (under other devices)
  • Select the Update Driver Software… menu item
  • Click Browse my computer
  • Click Let me pick from a list of device drivers on my computer
  • Scroll down the list and click Network Adaptors to select it, then click Next
  • Click the have disk button
  • Click browse
  • Go to c:driverswinethernetpro1000winx64ndis62 (if you put it in the default location or wherever you put it during installation) and select the e1k62x64.inf file.
  • Click Open
  • Click OK
  • Select the 82567LM-3 nic in the list and click Next
  • Click Yes on the compatibility warning dialog box
  • Click Close.

Source information:

·       Private Cloud Is The Future of IT, Free Training Coming Soon–Registration Open

o   Open HTTP: http://mschnlnine.vo.llnwd.net/d1/inetpub/danstolts/resources/2012/Add_Hyper-V_Role.wmv

o  

clip_image004[4]

 


http://mschnlnine.vo.llnwd.net/d1/inetpub/danstolts/resources/2012/2008r2sp1-Sysprep-Hyper-V_VM.zip

o   Windows Server 2008 R2 SP1 ISO as well as System Center ISO’s can be downloaded from http://aka.ms/lab

 


 

Hands-On Prerequisites

The format of the hands on is “keep up with the presenter if you can”. We will be going through the content and you can follow along, if you like. You will get a lab guide to use during the session or to take home with you and do it / finish it later. In the lab, we will be setting up the server infrastructure that will be needed to deploy System Center 2012 basic components in your own lab. This will include AD infrastructure and virtual machines that you can use to later install System Center (VMM, Operations Manager, Orchestrator, Service Manager) including instructions on getting networking between the machines working. If you do want to try to keep up, in the hands-on lab, make sure you bring a laptop with plenty available disk space. Also, come early to grab a seat with electricity. These seats are very limited so if you want one, arrive early. CAMP HANDS-ON LAB REQUIREMENTS: If you want to participate in Hands-On please bring your laptop with the following minimum requirements:

 

CAMP REQUIREMENTS: Please bring your laptop with the following minimum requirements:

§  4GB RAM is sufficient for building a simple AD domain (and 8GB will be a reasonable minimum to run a non-trivial scenario of VM deployment, which is optional for this event)

§  80GB of free disk space

§  x64 compatible processor with Intel VT or AMD-V technology

§  Basic install of Windows Server 2008 R2 SP1 with the Hyper-V Role enabled – Free download here

§  Also, please backup your system before coming (just in case)

Download Windows Server 2008 R2 SP1 and System Center 2012 to facilitate the scenarios in our technical demos. And for those who want to experience the next version of Windows, download the consumer preview of Windows Server 2012 and Windows 8.

Assumptions:

a)       Your hardware meets the requirements to run Windows Server 2008 R2 SP1 with Hyper-V

b)       You already have Windows Server 2008 R2 SP1 Running on your computer

c)        Network drivers are installed and working  LAN and Wireless

d)       Wireless Feature Enabled

e)       Hyper-V Role Installed

Prerequisite steps:

1)      Boot computer into bios (Enable or Verify BIOS settings (i.e. DEP & VT) For Hyper-V)

a.       Enable Data Execute Protection  (Security)

b.      Enable Virtualization  (Processor)

2)      Boot to Windows Server 2008 R2 SP1

a.       Enable Hyper-V role

                                                               i.      Add Wired Network Controller to configuration – Finish Install  then Reboot

                                                             ii.      Finish enable Hyper-V Role (auto-resumes after reboot)

b.       Enable Features

                                                               i.      Wireless LAN Service Feature

                                                             ii.      Desktop experience Feature [Optional, requires reboot]

 

Word Version of Lab-Guide-Phase-II-Setup-Private-Cloud-Foundation